How do I optimize system performance?

For the most part, system optimization occurs behind the scenes with built-in optimization features, scheduled maintenance and hands-on management by Application Administrators.

However, the way we use Collections can impact the performance of the system for better or worse. Here you will find our top 10 tips for users for optimizing the performance of Collections (and a link to more details):

Area	Details
Record details View	Only open the panels (aka tabs or screens) that you need to see and work with, and close any that you are done with.
Display Views	Limit the number of Views you have open at the same time. Working with Result set View and Record details View side-by-side is often sufficient. Again, if you have a View open and no longer need it, close it.
Related records View	This View performs best when the Search limit in the Relationship settings dialogue is low (10 is often sufficient); the higher the number, the slower the View is to load records. If you do not need the Show empty relationships option to be enabled, ensure that the slider is in the Off position as this will also improve performance.
Hierarchy browser	The lower the setting for Number of nodes per request in the Record Hierarchy settings dialogue, the better the performance of this View. If you do not need to enable Show equivalent terms, Show related terms and Show pseudonym terms, ensure that the sliders are in the Off position as this will also improve performance.
Thumbnail size	Set Thumbnail Size to small and Number of thumbnails to `1` in both Result set View and Gallery View.
Result set View	If you do not need to see thumbnails in the result set, do not include the media.reference column in the View. In general, performance is also improved by: limiting the number of fields to show as columns; limiting the number of Linked fields A type of field used to link one record to another. A Linked field is a drop list of values (records that the field can link to). When a link is made, the field stores a reference to the linked record (a linkref).; disabling Retain sorting, grouping and filtering.
Advanced search	Performance is better when only searching indexed fields. Non-indexed fields can be searched but without an index the search is much slower as Collections must query every record sequentially for your search value. To differentiate between indexed and non-indexed fields in the Fields list: Indexed fields are bold. Non-indexed fields are listed after indexed fields, and are clearly labelled as Not indexed.
Parent / child records	If your archival registry policy allows for it, limit the number of child records underneath a parent as far as possible.
Resource-hungry operations	Try to limit time-consuming and resource-hungry operations (e.g. imports; exports; large Search and replace operations) during work hours as these can impact performance of Collections for other users.
Log out	Rather than just closing the browser when you're done with Collections, log out of Collections; and be sure to close any browser tabs in which Collections was open.